I am still a fan of offering a pretty extensive collection of possible columns for display in the PLOG. The pilot could then choose, e.g., "GS (planned)" as well as "GS (actual)" at the end of the flight and print out the deviations between plan and actual values. In fact, it would be great if the user could choose different sets, give them names and save them for future use. In practice, I would put together a set of PLOG columns for planning named "planning", for flying namded "flying" and for archive purposes named "printing".Some users might want different sets depending on landscape and portrait orientation of their tablets. There could be a pre-defined default set for flying and planning to get started.

In my opinion, that would allow the maximum flexibility with the most usefulness.

-- Chris.

unless the achieved ground speed was shown as something like "120kt (+4)", and the leg time as "21min (-2)" ?

The advantage would be to highlight the fact that head/tailwinds were different from predicted.

I'm not keen on doing this. I don't fully understand what the benefit of knowing your average GS over the course of a completed leg would be. We'd need to write and test code to record it. We'd need columns to turn from white to blue to indicate that a "live" value had been recorded, and even once we'd done that, there'd be no way of comparing the average GS you achieved to the "planned" GS (or what it was "supposed" to be) anyway, unless we introduced another column.

Tim,

Some more suggestions for the live PLOG:

1) Can the Ground Speed and Time columns become 'live' columns so that the average leg speed and elapsed time are displayed in these when a leg completes.

2) Am I correct in assuming that the blue background highlight for the ETA/ATA column indicates that this is a 'live' column and will change values as the flight progresses? If this is the case and (1) above is implemented then can you colour the background blue on the ATA, GS and Time columns only once the leg has been completed and the actual (as opposed to planned) values are inserted.

Simon

Chris, don't confuse beta releases with public releases. The public releases of SkyDemon usually happen on the same day. There is an iOS beta, where all these new features are also being trialled, but it's private. You cannot do public beta testing on iOS.

Simon, good idea, we'll get that option added.

Mike, thanks, we'll review the NOTAM printed output. We'd have to hear some pretty strong support for moving user documents to the top of the document browser support before we would change the way that works.

Tim

NOTAM Print - Wordwrap is missing in printout, cuted output.

What do you think about reverse order in 'plates - document browser' menu -  user documents to displayed first. Background about this, I use to store i.e. checklists and the new printed PDF PLOG output in this user documents folder for direct access.  An extra 'user documents' toggle within the 'plates' menu would be fine as well.
 
-mike

IOS simply doesn't allow public betas. So sit back & relax. We will do the beta testing for you 😇

-mike

In the live plog context menu as well as "Remove from route" and "Insert waypoint before" could we also have "Show on map" which would return to the map screen and display as if a "Find waypoint" had been requested in the map screen? Also maybe have a "Route direct" option which would remove all intermediate waypoints from the current position to the selected waypoint?

@Chris:  I think the answer might be that it's much easier to post beta versions for Android as you don't have to go through the app store and its release process every time as you do with iOS apps.

Tim, has the iOS veraion of SD taken a back seat now? It seems as if the new features are added to Android first, with the iOS lagging behind. I am not getting any update notices from the Appstore for SD.

-- Chris.

Thanks Mike. We identified a bug which was stopping lots of frequencies from being added to the live PLOG and radio screens (it's the same code).
You should see loads more in the next beta, and you should always see the frequencies for your takeoff/landing/alternate airfield if it's within 30 miles.
Do let me know if there are still any scenarios where you'd expect to see frequencies when you're in flight but they do not appear.